OpenEdge Getting Started:<br />Installation and Configuration Installation .ini file

The installation .ini file is user-defined. The format of the installation .ini file follows, where n represents the total number of configurations you are installing.

You can specify as many of the supported languages as you want in the Language Choice section. You can specify lang=All to install all of the available languages, but this is not recommended because of disk space considerations. Each language that you select will require approximately 8MB of disk space.

The first time you install OpenEdge you must set a default language (see the Language Default section in the example below). Be sure to type the language values exactly as they appear in the following example of an .ini file.

Create a response file. You can produce this file using one of the following methods:

Programmatically (recommended method) using the Response (-r) command-line parameter.

This method is designed to provide Application Partners (APs) a streamlined approach to integrate the OpenEdge installer into an application installer. Using this method, an Application Partner can use the supplied response file template to programmatically create an OpenEdge installation response file. This response file is packaged and shipped with the AP’s application; when the AP’s application is installed on a customer site, the OpenEdge installation information is read from the response file, enabling the customized install to be performed silently. See the "Creating the response file automatically" section.

Manually editing a response file.

An alternative approach to the programmatic method. For more information on manually creating a response file, see the "Creating the response file manually" section.

Play back the Silent Installation using the Silent (-b) command-line parameter. The OpenEdge Silent utility runs on its own without your intervention. The syntax for running the OpenEdge Silent Installation utility in batch mode follows:


proinst -b[-n] <path>/<response-file-name> <path>/<logfile-name>]

Note: Do not leave a space between command line command entries and options. Also, neither command line entries nor options are case sensitive.


-b <path>/<install-ini-file>

Specifies that the install is a batch install.

Specifies the install.ini file. If not specified, proinst searches the current directory for the default install.ini file, install.ini. If no .ini file is found, the batch installation fails.


-r <path>/<responsefilename>

Specifies that the response will be automatically recorded. The install.ini file that contains all responses you recorded during the automatic record process are contained in this file.

-n

Specifies that the install display notification of current installation phase and percent complete.


-l <path>/<logfile-name>

Specifies the name of the installation log file. If no filename is specified for the log file, the OpenEdge Installation Utility uses the default log filename of install.log. If no directory is specified for the log file, it is saved to the directory pointed to by the first of the following environment variables found by the Installation Utility:

TMP

TEMP

TMPDIR

Note: In the syntax above, directory pathname refers to the directory where the OpenEdge Installation Utility, the installation support files, and the archive files can be found.

Creating the response file automatically

proinst -b /test/install.ini -l /log/test.log

All your installation choices are automatically recorded in a response file. If you do not specify a filename the install creates the file $TEMP/install.ini. Use the following syntax to initiate a response file:

Creating the response file manually

proinst -r [`<path-to-file>`\`response-file`]

You can create and edit a response file such as the oesetup.ini example response file template shown in the "install.ini (1 of 3)" section. Although all sections of the response file are required, you do not need to add each of these required sections in the order presented; the installer only retrieves the specific data it needs regardless of where the information is located in the response file.

Create a new text file, using any text editor.

Enter response file required sections. Note that section names are contained in square brackets. For example:

[Product Configuration] — Company name, serial code, and product control numbers

[Type and Destination] — Installation type and installation destination directory.

[Server Engine] — Type of database

[Language Default] — User-defined default language for PROMSGS

[International Settings] — User-defined default character set and number format.

Edit the necessary data within each section name, as needed for your installation. Many of the data entries consist of name=value pairs. For example, for [Web ServerType] the following name=value pairs exist: Web ServerType=type and CopyHTMLFiles=yes.

In contrast, other sections require more information to complete. For example, the following table explains how to determine your numeric format. The indicators _szNumsep and _szNumdec in the [International Settings Dialog] of the sample response file are assigned numeric values that correspond to the location of a number separator and decimal point, respectively. To determine the number format as defined in the sample response file, note the combination of the numbers defined for each of these items and then reference these numbers to determine your numeric format, as shown in the following table:


This value represents the location of the number separator	This value represents the location of the decimal separator	Sample display format	Format description
39	44	1’234,56	apostrophe, comma
39	46	1’234.56	apostrophe, period
44	36	1’234$56	comma, dollar
44	46	1,234.56	comma, period
46	44	1.234,56	period, comma
46	36	1.234$56	period, dollar
32	44	1 234,56	space, comma
32	46	1 234.56	space, period
160	44	1 234,56	non-breaking space, comma
160	46	1 234.56	non-breaking space, comma

Save and close the file.